Overview
What is NGINX?
NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over…
NGINX review
NGINX review
great
Recommended product
NGINX the champion
Using as a cache
Using SSL Offloading
Solution for Reverse Proxy
NGINX Forward Proxy is the way to go!
Using NGINX when building POC labs in Azure and AWS to demonstrate IaaS solutions
NGINX Review
NGINX Review
NGINX Review
Nginx is a powerful tool
NGINX simple review
!yxorp esrever a sa XNIGN gnisU
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Popular Features
- Installation (18)9.494%
- Application server performance (18)8.686%
- Administration and management (18)8.080%
- Security management (18)8.080%
Reviewer Pros & Cons
Pricing
What is NGINX?
NGINX, a business unit of F5 Networks, powers over 65% of the world's busiest websites and web applications. NGINX started out as an open source web server and reverse proxy, built to be faster and more efficient than Apache. Over the years, NGINX has built a suite of infrastructure software…
Entry-level set up fee?
- Setup fee optional
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
25 people also want pricing
Alternatives Pricing
What is Zend Server?
Zend Server, developed by Zend, acquired by Rogue Wave Software in 2017 and then by Perforce in 2019 with that company's acquisition of Rogue Wave, is an All-in-One PHP Application Server that aims to improve web app deployment, debugging, and monitoring. Additionally, ZendPHP Enterprise offers…
Product Demos
CVE-2016-1247 Nginx (Debian-based) Vulnerability - Root Priv. Escalation PoC Exploit Demo
Nginx Web Server configuration with Examples
Load Balancing with NGINX
Access your internal websites! Nginx Reverse Proxy in Home Assistant.
How to Serve Static Content
Using NGINX Open Source for Video Streaming and Storage
Features
Application Servers
An Application Server provides services and infrastructure for developing, deploying, and running applications
- 7.3IDE support(10) Ratings
Support for a number of different programming environments or IDEs
- 8Security management(18) Ratings
Integrated security management for applications
- 8Administration and management(18) Ratings
Ease of management via administration console
- 8.6Application server performance(18) Ratings
Speed of deploy time, initialization time and other performance metrics
- 9.4Installation(18) Ratings
Ease of download and installation
- 7.9Open-source standards compliance(16) Ratings
Support for open-source standards like J2EE
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is NGINX?
- NGINX Plus: An all‑in‑one load balancer, web server, and content cache.
- NGINX Controller: Centralized monitoring and management for NGINX Plus.
- NGINX App Protect: Web application firewall, powered by F5
- NGINX Unit: Lightweight application server, with support for multiple languages and a dynamic REST API‑driven configuration
- NGINX Ingress Controller: Traffic management solution for cloud‑native apps in Kubernetes and containerized environments.
- NGINX Service Mesh: Lightweight, Turnkey, Developer-Friendly Service Mesh Using NGINX Plus as an Enterprise Sidecar
NGINX Features
Application Servers Features
- Supported: IDE support
- Supported: Security management
- Supported: Administration and management
- Supported: Application server performance
- Supported: Installation
- Supported: Open-source standards compliance
Additional Features
- Supported: NGINX: Fast, light web server and reverse proxy
- Supported: NGINX Plus: All‑in‑one Load Balancer, Web Server, and Content Cache
- Supported: NGINX Plus: Security controls, High Availability, Dynamic Modules
- Supported: NGINX App Protect: Layer 7 Attack Protection
- Supported: NGINX Controller: Centralized Traffic Management and Monitoring
- Supported: NGINX Controller: Role-based Access Controls
- Supported: NGINX Unit: Multi-language Application Server
NGINX Screenshots
NGINX Integrations
- Microsoft Azure
- Mirantis Kubernetes Engine
- Kubernetes
- ForgeRock Identity Platform
- Amazon Elastic Compute Cloud (EC2)
- Red Hat Enterprise Linux (RHEL)
- DeviceAtlas
- Red Hat OpenShift
- Google Cloud Platform
- OpenStack
- Cedexis
- IDFConnect
- PingIdentity
- Phusion Passenger
- Stealth Security
NGINX Competitors
NGINX Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Frequently Asked Questions
NGINX Customer Size Distribution
Consumers | 0% |
---|---|
Small Businesses (1-50 employees) | 0% |
Mid-Size Companies (51-500 employees) | 50% |
Enterprises (more than 500 employees) | 50% |
Comparisons
Compare with
Reviews and Ratings
(137)Attribute Ratings
Reviews
(1-19 of 19)great
- flexible maintenance
- easily scalable
- SAML idp integration and routing
Can't get a better backend load balancer than nginx
- Load balancer
- Load sharing
- Web server
- Reverse Proxy
- Community support is limited
NGINX the Web Server you can count on!
- Host Web Sites
- Use it as a proxy server
- COnfiguring several virtual hosts.
- Improve on the official docs to have several example scenarios.
- Improve on the error messaging.
- Make it easier to host several PHP versions on the same machine.
Nginx outperforms other web servers
- Performance
- Reliability
- Low configuration
- Rarely used in development
- Difficult to tell if it changed values from a server behind it
- Limiting the number of simultaneous connections or requests coming from one address
- Prompt Static content delivery
- code caching and reverse proxy server
- NJS Scripting Language.
- Much more areas of application
- A bit hard to implement.
NGINX, a powerful 3 in 1 solution for budget conscious startups.
- Load balancing.
- Proxy server.
- Config files aren't as straightforward as Apache.
NGINX Review
- SSL/TLS encryption - Incredibly simple to configure and use.
- Gzipping - Quickly and easily compress responses to save network cycles.
- Lack of logging tools - Simply writes logs to files that you have to manually navigate.
- No GUI - All configuration from a console. This could be a pro or a con to some.
Great lightweight web server.
- Stability. It runs quietly and never goes down.
- Flexibility. It can run in all the Linux distro.
- Compatibility. It works with PHP and MYSQL well.
- It's free.
- Community. Compare to Apache, Nginx has much smaller community support. You do not have lots of resources you can use when you encounter a problem accept digging into it and trying to figure it out yourself.
- Lacks Large Scale Experience. Nginx is not the first choice for enterprise level architecture. Most large companies will use Apache instead of Nginx when it comes to large scale architecture. Here is where Nginx's lightweight advantage becomes their con.
- Lack of multiple modules compatibility. Because Nginx is a lightweight focused server, it cannot be used with some other modules. That also makes Nginx favorable for people with small websites.
Only possible choice to serve our business
- Great community
- A lot of documentation available
- High-performing
- Easy to configure
- Cache static assets
- Multi-threaded support
- A user-friendly UI console to test some configurations in a test server
Nginx - great alternative for Apache Server
- Reliable load balancing capabilities
- Caching of static assets is great
- SSL handling is good
- Relatively simple configurable proxy solution
- Open source hence accessibility is easy to larger audience
- Nginx plus is a bit on higher end on pricing for small organisations
- Automatic Nginx configuration & services update for open source version is something which would be a welcoming step. Currently everything needs to be done manually
- Web GUI console could be a slight better and some configurations from there itself would be highly appreciated
Fast and configurable
- Powerful and flexible configuration
- Low resource usage with low overhead
- Well-supported on major operating systems
- Less well-known in communities than Apache, making it more difficult to find documentation and support
- Requires manual configuration for integration with some popular CMS
Nginx - Best Web Server for High-Traffic Websites
- Very low memory usage. Can handle many more connections than alternatives (like Apache HTTPD) due to low overhead. (event-based architecture).
- Great at serving static content.
- Scales very well. Easy to host multiple Nginx servers to promote high availability.
- Open-Source (no cost)!
- Less community support compared to Apache
- Less extensive list of modules compared to Apache
The most reliable load balancer I've ever used
- Static assets caching
- Extremely simply configurable proxy solution
- Load balancing is awesome
- The robustness is on the top
- Steep learning curve: you'll spend lots of time to read all manuals and specs before you can configure it correctly
- SSL handling is poor
The Most Reliable Load Balancer You'll Ever Use
- Straight-forward configuration format that users of all skill levels can learn, and yet is powerful enough for the huge breadth of features that Nginx provides.
- Massive scale right out the box. We've never had a Nginx instance overwhelmed by requests, and if we did it would be trivial to spin up more Nginx instances to handle the load.
- SSL termination means that we can deliver content over HTTPS without needing our individual services to require TLS support. This saves us a lot of time and headache while keeping us secure.
- Nginx is open-source and free, meaning that anyone can use it to power their services, from individual projects to billion-dollar websites.
- The open-source flavor of Nginx does not support automatic service discovery. In the time of Docker containers, Kubernetes and other managed cloud services, it can be difficult to manually update Nginx configurations as services change.
- Nginx is quite heavy for smaller projects and low-traffic scenarios. It requires knowledge of operating and configuring, which is separate from operating the main web server. There are managed alternatives that will get web services up faster and be more reliable.
- Nginx-plus has some very valuable tools that projects of any size could take advantage of. Unfortunately, it is very expensive as it includes SLA and support, putting it out of reach of all but the most well-funded projects.
Hail to the king of of the lightweight web!
- Nginx is typically blazing fast. It's hard for other web servers to touch it in terms of raw speed and efficiency.
- Nginx has a simple and intuitive configuration language which is easier for me to keep in my head than the more verbose Apache syntax.
- Nginx is very powerful as a web server, offering the ability to utilize many of the same features as Apache, sometimes in even better ways.
- Nginx works great as a reverse proxy, too! It can sit in front of a separate server, or even a cluster of servers, and intelligently handle serving requests to and responses from those servers, including a highly-configurable caching layer.
- Nginx often requires some initial configuration. It's worth doing, because you'll end up with great results, but it can be slightly daunting for someone to get started using it. Apache might have a leg up in that regard--When you install Apache, typically it's just about ready to do what you want already. But the issue with Apache is that most people skip the extensive tuning phase required after that, and with nginx it becomes more just a part of the configuration process.
- Sometimes, the configuration syntax, even though it's powerful and terse, isn't the most intuitive. Luckily there's plenty of documentation about what things mean and how to accomplish certain things. There may not be much that can be done about this--to have a powerful web server, you need a powerful-enough configuration language.
- The nginx brand is somewhat fragmented, and it can be confusing. There's the open source nginx web server, which I've primarily been referring to. But then there's NGINX Plus, a premium subscription-based service which works with a range of other NGINX products (NGINX WAF, NGINX Amplify, NGINX Controller). I've met a number of people who weren't very familiar with nginx, and instinctively went to nginx.com first, and from there it seems like everything costs money. It's only when they realize there's a different site, nginx.org, that they find what they went looking for.
- Nginx excels at serving static assets (images, cached files).
- Nginx is fantastic for load-balancing and routing requests to back-end application servers.
- Nginx is built for scaling and is an excellent solution for high-traffic websites.
- Nginx has good features for protecting against certain security exploits.
- Nginx has some peculiarities or "gotchas" that take getting used to.
- Nginx could improve at SSL handling.
- Nginx is the best asynchronous server but I could see using Apache for process-based (threaded) serving of dynamic assets as a back-end behind Nginx. So I don't think Nginx should necessarily improve in this regard as much as it's choosing the right tool for the job—Nginx for static serving, other, process-based servers for dynamic serving.
We currently have 5 different deployments of Nginx, and everyone in the company that deploys production apps uses them.
The main business problem addressed by Nginx was definitely speed and load balancing. Before using Nginx + Passenger, we had Apache servers in front of Mongrel for our rails apps, and they not only were slow and memory intensive, the only load balancing strategy available with that setup was round-robin allocation of incoming web requests to different app servers. With Nginx, it acts as a load balancing proxy as well and keeps track of which app servers are free to receive new requests. This resolves bottlenecks in our server's performance.
- Nginx works really well for serving static files. You can let requests for static files and assets pass directly through to the file system and Nginx will serve them really fast, without touching your web app processes.
- Nginx does a great job with load balancing. You can set up different load balancing strategies, but the default load balancer it comes with out of the box works very well already -- better than any round-robin approach because it checks for availability of the resource before handing off the incoming request.
- Nginx is more memory efficient and generally faster than Apache. It has a small footprint, which can be very helpful, especially if you're running on a VPS.
- Nginx has not crashed on me even once. The robustness of Nginx overall is very impressive.
- You can apply configuration changes to Nginx without needing to restart the server. You can also do reloads of the config without dropping any web requests because Nginx provides a global queue where requests can be held while it reloads the config.
- There's no configuration wizard. I had to read their docs every time I make a change to the Nginx config files.
- Deploying rails apps with Nginx + Passenger requires a recompilation of Nginx. It would have been better if Nginx supported a plugin system that would allow you to plug in some rails app servers into it.
- There's no easy way to tell which incoming request was sent to which back-end app server. You have to do advanced tricks to keep track of those things, in case you need to see what's happening behind the scenes for debugging.
NginX is a blazing fast web server with native load balancing .. considering it yet?
- Nginx's best feature is what it was designed for in the first place, providing a high amount of simultaneous connections with less hardware resources. NginX is at minimum, twice as fast as Apache with static requests, and equal to Apache with PHP requests.
- Nginx was created appr. 5 years after Apache, giving it the benefit of Apache's hind-sight, which has allowed NginX to be designed to better handle, or simply bypass and hand-off processes to better equipped software.
- NginX includes quite a few very useful performance enhancing tools built in, such as advanced caching techniques (converting proxied dynamic content to static content for faster caching), native reverse proxy support, and best of all, built-in load balancing that is very easy to use.
- The NginX setup and deployment is very easy, as the entire configuration is located in 2 files, consisting of a general server config, and a site-specific config for virtual hosts, allowing the greenest of Linux admins to easily deploy a web server.
- Even though Nginx is the 2nd most used web server, it is rarely recognized by anyone outside of an IT field that uses it directly. This makes it a very hard sell, especially within start-up companies (a great place for NginX) relying upon VC funding, where brand recognition of the providers/manufacturers used in your IT environment can be a factor in funding.
- Due to being less known, NginX does lack on advanced community support along with modules and add-ons when compared to Apache, luckily the community support available is generally more than enough. The same goes for locating experienced NginX administrators, but again, the learning curve is very small. allowing staff to be adequately trained in a short amount of time.
- Due to the first point I made, a lot of software does not come with pre-configs for NginX
Nginx - Simple, Reliable, Featureful, Enjoyable
- dynamic routing of ingress traffic to Docker containers
- load balancing web applications
- proxying requests to different applications
- Proxy: an extremely simple proxy solution. And again, easy to write and read configuration.
- Cache: cache static assets.
- Dynamic Routing of Ingress Traffic: Using tools like confd, you can dynamically rewrite nginx rules and route traffic to Docker containers.
- I've yet to run into a pain point with nginx.